Method and apparatus for MAC layer inverse multiplexing in a third generation radio access network

ABSTRACT

A channel inverse multiplexer/multiplexer (IMUX/MUX) ( 14   a ) of a MAC sublayer ( 14 ) of a UTRAN RNC ( 11 ) for providing to a UE ( 18 ) traffic (communication signals including in general both control and user data) at a higher rate than the UE can accept over a single channel. The channel IMUX/MUX performs inverse multiplexing of traffic for downlink, and multiplexing of traffic on uplink, and does so in a way that is transparent to all other layers/entities of the UTRAN ( 11 - 17 ) and to the UE ( 18 ).

CROSS REFERENCE To RELATED APPLICATIONS

[0001] Reference is made to and priority claimed from U.S. provisional application Ser. No. 60/333,411, filed Nov. 26, 2001, entitled MAC LAYER INVERSE MULTIPLEXING IN 3G RAN.

FIELD OF THE INVENTION

[0002] The invention relates to services of the media access control (MAC) layer of a radio access network (RAN). More particularly, the invention relates to procedures for mapping one logical channel, by which user or control data are provided to the MAC layer from the radio link control (RLC) layer, to multiple transport channels, by which user or control data are provided by the MAC layer to the physical (PHY) layer.

BACKGROUND OF THE INVENTION Context

[0003] As shown in FIG. 1, according to 3G WCDMA (Third Generation Wideband Code Division Multiple Access), in communicating via wireless communication, a mobile user equipment (UE) 18 interfaces with a UTRAN (universal mobile telecommunications system (UMTS) terrestrial radio access network) Node B 17 (also sometimes called a base station) over a so-called Uu interface. The UTRAN Node B in turn communicates with a UTRAN radio network controller (RNC) 11 over a so-called Iub interface, and the RNC communicates with a core network (CN) entity, either a mobile switching center (MSC) or a serving GPRS (general packet radio system) support node (SGSN), over a so-called Iu interface, and also communicates with other RNCs over a so-called Iur interface. The Iu interface is more specifically either an Iu circuit-switched interface IuCS between a UTRAN RNC and an MSC, or an Iu packet-switched interface IuPS between a UTRAN RNC and an SGSN.

[0004] There are a set of protocols used by a UE and a UTRAN in communicating across the Uu interface which are jointly called the WCDMA protocol; the different protocols making up WCDMA are called protocol layers. The lowest layer, as illustrated in FIG. 2A, is a physical layer (PHY), denominated layer 1 (L1), and resides in the UE, the node B and the RNC, although an MDC (macro-diversity combining) component of L1 does not reside in node B and that component is the only component of L1 that resides in RNC; however, by locating the MDC component of L1 in RNC, soft handover can be supported, during which data coming from different branches are macro-diversity combined in the RNC. A layer 2 (L2) resides in RNC and, in case of configurations supporting HSDPA (High Speed Downlink Packet Access), also resides in node B. See FIG. 2A showing L2 only in RNC and see FIG. 2B showing L2 extended to reside in both RNC and node B as the MAC-hs entity in node B. L2, in general, consists of a media access control (MAC) sublayer and a radio link control (RLC) sublayer, as well as other sublayers not relevant to the invention, such as the PDCP (Packet Data Convergence Protocol) sublayer and the BMC (Broadcast Multicast Control) sublayer. PHY offers transport channels to the MAC sublayer, which in turn offers logical channels to the RLC sublayer.

[0005] Note that the data flows from the FP layer over the Iub interface are different in FIG. 2A (showing case for configuration not supporting HSDPA) and FIG. 2B (showing case for configuration supporting HSDPA). A transport channel is defined in UTRAN as a channel between the MAC layer (excluding MDC) and L1, and therefore in a case where HSDPA is not supported, transport channels exist on Iub interface. Also, because Node B in such a case does not contain any L2 functionality, the PDU (Protocol Data Unit), which is transmitted over the Iub interface, is a Transport Block (equal to a MAC PDU), i.e., no additions or changes the MAC PDU/Transport Block are made by Node B.

[0006] However, in case of a configuration supporting HSDPA, as in FIG. 2B, L2 is extended to the Node B, and if transport channels are defined to be all channels between MAC layer and L1, then in this case the transport channel is a channel between MAC-hs and L1, i.e. it is an internal channel in Node B. On Iub, the data packet is transmitted as a MAC-d PDU, so that the packet is not a complete MAC PDU. Before it is made into a complete MAC PDU, the packet must be processed by MAC-hs, which adds a MAC-hs header at the head of an already existing MAC-d header. Thus, the structure of the PDU is not complete when it comes to the Node B. Therefore there are different names for the data flows from the FP layer over the Iub interface for the case of a configuration supporting HSDPA and one that does not.

[0007] The WCDMA FDD (frequency division duplex) communication between a UE and an SRNC through the defined protocol stacks is illustrated in FIGS. 3A-C for three different applications. FIGS. 3A and 3B illustrate the protocol stacks for the DCH (dedicated channel, a transport channel) and DSCH (dedicated shared channel), respectively. The data coming from the DTCH (dedicated traffic channel) and DCCH (dedicated control channel) logical channels are mapped either onto the DCH (as in FIG. 3A) or the DSCH (as in FIG. 3B), using the services of MAC-d or MAC-d/MAC-c/sh, respectively. From the MAC layer, the data are communicated to a Node B using the services of the FP layer. At the node B, the data are provided to the UE over the air interface via the services of L1.

[0008]FIG. 3C illustrates the case when the configuration provides support for HSDPA. In this case the data, which is received from the RLC layer by the MAC layer over logical channels, are mapped onto so-called MAC-d data streams using the services of the FP layer. At a Node B, these MAC-d data streams are mapped to physical channels using the services of the MAC-hs and L1. The protocol stacks in FIGS. 3A-C all use, for the TNL (Tranport Network Layer, discussed below) at the Iub and Iur interfaces, the service of ATM (Asynchronous Transmission Mode) and AAL2 (ATM Adaptation Layer Type 2) protocols.

[0009] It should be understood that in case of an HSDPA application, such as illustrated in FIG. 3C, the MAC-d data streams correspond to the transport channels at an Iub interface.

[0010] As illustrated in FIG. 4, the general protocol model for UTRAN interfaces consists of two main (horizontal) layers, the Radio Network Layer (RNL), and the Transport Network Layer (TNL). All UTRAN telecom-related issues are visible only in the RNL, and the TNL represents standard transport technology that is selected to be used for UTRAN, but without any UTRAN specific requirements. The RNL includes layers 1-3. The TNL provides the capability of transporting the Frame Protocol PDUs and Application Protocol signalling messages over Iub, Iur, and Iu, using ATM technology. ATM technology refers not only to ATM protocol but to all related protocols (ATM, AAL2, AAL 5 ) and to any physical transmission appropriate for an ATM interface. The TNL at the Iub interface manages only ATM-related issues. All other functions and protocol layers are handled by the RNL.

[0011] As is indicated in FIG. 4, the general protocol model for UTRAN Interfaces also consists of three (vertical) planes: a Control Plane, a Transport Network Control Plane, and a User Plane. The Control Plane includes the so-called Application Protocol and the Signalling Bearer for transporting the Application Protocol messages. Among other services it provides, the Application Protocol is used for setting up bearers (i.e. a Radio Bearer and a Radio L1 nk) for the RNL. In the three-plane structure, the bearer parameters in the Application Protocol are not directly tied to the user plane technology, but are rather general bearer parameters. The Signalling Bearer for the Application Protocol may or may not be of the same type as the Signalling Bearer for the ALCAP (Access Link Control Application Part). The Signalling Bearer is always set up by Operations and Management (O&M) actions (under the direction of an Operations and Management Center or OMC).

[0012] The User Plane includes the data streams and the data bearers for the data streams. The data streams are characterized by one or more frame protocols (FPs) specified for that interface.

[0013] The Transport Network Control Plane does not include any RNL information, and is completely in the Transport Layer. It includes the ALCAP protocol(s) needed to set up the transport bearers (Data Bearers) for the User Plane. It also includes the appropriate Signalling Bearers needed for the ALCAP protocols.

[0014] Also as illustrated in FIG. 4, the Data Bearers in the User Plane and the Signalling Bearers for the Application Protocol both belong to a Transport Network User Plane. (As mentioned, the Data Bearers in Transport Network User Plane are directly controlled by the Transport Network Control Plane during real-time operation, but the control actions required for setting up the Signalling Bearers for Application Protocol are considered O&M actions.) Thus, there is a Control Plane and a User Plane when viewed from the RNL, and a differently constituted (Transport Network) User Plane and (Transport Network) Control Plane when viewed from the TNL.

[0015] The End-to-End Bearer Service and the UMTS Bearer Service are illustrated in FIG. 5. On its way from a TE (terminal equipment, and can be part of a UE, as indicated as an MT in FIG. 5) to another TE, the traffic must pass different bearer services of one or more networks. A TE is connected to the UMTS network by use of a Mobile Termination (MT), which in combination with the TE makes up a UE. The End-to-End Bearer Service on the application level uses the bearer services of the underlying networks, and is conveyed over several networks, not only the UMTS network. The End-to-End Bearer Service used by a TE is realized using a TE/MT Local Bearer Service, a UMTS Bearer Service, and an External Bearer Service.

[0016] The problem solved by the invention

[0017] According to 3GPP TSG RAN specifications (such as e.g. 3GPP TS 25.401), when an RNC is communicating with a Node B so as to ultimately communicate with a mobile phone, (see FIG. 2), each transport channel is conveyed across an Iub interface by a dedicated AAL2 connection (see FIG. 3), which is provided to a Frame Protocol (FP) layer 16 (see FIG. 2). An AAL2 connection is one realization of a transport bearer in UTRAN. The FP layer 16 is a part of the RNL, whereas the AAL2 is a part of the TNL. The WCDMA L1, as a part of the RNL, can provide macrodiversity for the data streams when they are in soft handover; in other words, the WCDMA L1 can handle the same UE data streams from two different Node Bs. Otherwise, the WCDMA L1 of the RNL is transparent to the data stream, i.e. the WCDMA L1 of the RNL does not in any way affect or process the data stream if the mobile phone is not in soft handover. (This is a simplification and may not always be true; the WCDMA L1 is always doing processing like interleaving/deinterleaving and channel coding/decoding in the Node B for each data stream.)

[0018] Note that there is an L1 for the RNL (WCDMA Layer 1), which handles macrodiversity and there is an L1 functionality for the TNL (TNL Layer 1), which handles the physical transmission below the ATM protocol on TNL. The RNL/TNL protocol stack cannot be compared with the seven-layer open systems interconnect (OSI) model.

[0019] The specifications further provide that the transport bearers (i.e. AAL2 connections in case of ATM transport) are controlled (set up, released, modified) by an AAL2 signaling protocol, which allows transport bearers to have a bit rate of up to a maximum of 2048 kbit/s. In UTRAN Rel5 (release 5), transport channels are specified that can exceed the 2048 kbit/s maximum rate of the AAL2 signaling protocol.

[0020] Therefore, what is now needed (because of release 5) is a way to enable a UTRAN (and more specifically an RNS) to use the AAL2 signaling protocol with transport channels conveying user and/or control data at bit rates in excess of the maximum of 2048 kbit/s, or in other words, a way to provide an AAL2 connection with (high capacity) radio bearers per UTRAN Rel5. Ideally, what would be provided could be used at both an Iub interface and an Iur interface.

SUMMARY OF THE INVENTION

[0021] Accordingly, a first aspect of the invention provides a radio network element for communicating to a mobile user equipment (UE) a higher rate data flow received from a core network (CN) entity, the higher rate data flow being provided to the radio network element at a higher rate than the UE can accept on a single channel, the radio network element characterized by: a radio link control (RLC) sublayer including a radio bearer service, responsive to the higher rate data flow, for providing a corresponding RLC data flow for downlink to the UE; a media access control (MAC) sublayer, responsive to the RLC data flow, for providing a plurality of corresponding MAC data flows at a rate low enough to be acceptable to the UE; a framing protocol layer (FP layer), responsive to the MAC data flows, for providing corresponding transport network layer data flows; and an admission control (AC), responsive to radio access bearer parameters provided by the CN entity, for providing commands to the MAC sublayer specifying how the MAC sublayer is to allocate resources so as to communicate the higher rate data flow to the UE; and further characterized by the MAC sublayer in the radio network element including a channel inverse multiplexer/multiplexer (IMUX/MUX), responsive to the RLC data flow, for providing the plurality of corresponding MAC data flows at a rate low enough to be acceptable to the UE, and for including with each lower rate data flow information indicating how the lower rate flows are to be combined by the UE, the lower rate data flows being suitable for transmission by the FP layer according to a standard protocol not taking into account that the lower rate data flows are in combination the RLC data flow corresponding to the higher rate data flow.

[0022] In accord with the first aspect of the invention, in sending to a CN entity a plurality of transport network data flows received from the UE, the channel IMUX/MUX may be further responsive to a plurality of corresponding MAC data flows, and may provide, at the direction of the AC, a single corresponding RLC data flow for transmission to the CN entity as a higher rate data flow.

[0023] In a second aspect of the invention, a radio access network is provided including a Node B and also including a radio network element in accord with the first aspect of the invention.

[0024] In a third aspect of the invention, a method if provided by which a radio network element communicates to a mobile user equipment (UE) a higher rate data flow received from a core network entity, the higher rate data flow being provided to the radio network element at a higher rate than the UE can accept on a single channel, the method characterized by: a step in which a radio link control (RLC) sublayer including a radio bearer service, responsive to the higher rate data flow, provides a corresponding RLC data flow for downlink to the UE; a step in which a media access control (MAC) sublayer, responsive to the RLC data flow, provides a plurality of corresponding MAC data flows at a rate low enough to be acceptable to the UE; a step in which a framing protocol layer (FP layer), responsive to the MAC data flows, provides corresponding transport network layer data flows; and a step in which an admission control (AC), responsive to radio access bearer parameters provided by the CN entity, provides commands to the MAC sublayer specifying how the MAC sublayer is to allocate resources so as to communicate the higher rate data flow to the UE; and further characterized in that the MAC sublayer in the radio network element performs a channel inverse multiplexing/multiplexing using a channel inverse muliplexer/multiplexer (IMUX/MUX), responsive to the RLC data flow, and in so doing provides the plurality of corresponding MAC data flows at a rate low enough to be acceptable to the UE, and includes with each lower rate data flow information indicating how the lower rate flows are to be combined by the UE, the lower rate data flows being suitable for transmission by the FP layer according to a standard protocol not taking into account that the lower rate data flows are in combination the RLC data flow corresponding to the higher rate data flow.

[0025] In accord with the third aspect of the invention, in sending to a CN entity a plurality of transport network data flows received from the UE, the channel IMUX/MUX may be further responsive to a plurality of corresponding MAC data flows, and may provide, at the direction of the AC, a single corresponding RLC data flow for transmission to the CN entity as a higher rate data flow.

[0026] It should be understood that as the description to follow will show, nothing about the invention restricts its application to the Iub interface; it is just as applicable to the Iur interface. For the Iur interface, the demultiplexing (i.e. inverse multiplexing)/multiplexing is done for communication between a MAC-d in a SRNC and a MAC-c/sh in a CRNC, but the invention is otherwise as applied to the Iub interface, i.e. the invention is fundamentally unchanged: for data rates exceeding 2048 kbit/s, using a plurality of AAL2 s for a single logical channel.

BRIEF DESCRIPTION OF THE DRAWINGS

[0027] The above and other objects, features and advantages of the invention will become apparent from a consideration of the subsequent detailed description presented in connection with accompanying drawings, in which:

[0028]FIG. 1 is block diagram of a wireless communication system of a type in which the present invention can be implemented, including an RNC (radio network controller), a node B, and a UE (user equipment);

[0029]FIG. 2A is a more detailed block diagram of a portion of the wireless communication system of FIG. 1, showing a channel IMUX/MUX (inverse multiplexing/multiplexing) entity of the invention, the node B being configured in a way that does not support HSDPA (high speed downlink packet access);

[0030]FIG. 2B is another more detailed block diagram of a portion of the wireless communication system of FIG. 1, again showing a channel IMUX/MUX entity of the invention, with the node B here being configured in a way that does support HSDPA;

[0031]FIGS. 3A and 3B are block diagrams illustrating the protocol stacks for the DCH (dedicated channel) and DSCH (dedicated shared channel), respectively, according to the prior art;

[0032]FIG. 3C is a block diagram showing the radio interface protocol architecture of HSDPA without MAC-c/sh, according to the prior art;

[0033]FIG. 4 is a block diagram showing the general protocol model for UTRAN interfaces, consisting of two main (horizontal) layers, the Radio Network Layer (RNL), and the Transport Network Layer (TNL), according to the prior art; and

[0034]FIG. 5 is a diagram illustrating the End-to-End Bearer Service and the UMTS Bearer Service, according to the prior art.

BEST MODE FOR CARRYING OUT THE INVENTION

[0035] Referring now to FIGS. 2A and 2B, the invention is a channel inverse multiplexer/multiplexer (IMUX/MUX) 14 a implemented in a UTRAN RNC 11, and is of use when the RNC 11 sends across an Iub interface to a Node B 17 a 17 b downlink data traffic/flow P11 P12 P13 (conveying control and user traffic, in general) for subsequent delivery by the Node B to a UE 18 (across a Uu interface), the RNC receiving the data traffic/flow it conveys to the Node B from a CN entity (not shown), such as an MSC or a SGSN.

[0036] According to the invention, when data traffic is to be communicated by the RNC 11 to the Node B 17, a so-called Admission Control/Packet Scheduler (AC/PS) module 12 (the PS aspect providing packet data related functionalities in connection with packet switched connections from a SGSN), implemented in layer 3 (L3) of the RNC, sets up multiple transport channels (TrCHs) to be used in providing a single radio bearer (RB) service whenever the data rate for the RB would otherwise exceed some predetermined maximum data rate, such as 2 Mbits/s. In setting up TrCHs for communicating user packets (i.e. for a packet-switched connection), the AC/PS may use radio access bearer (RAB) parameters (see FIG. 5) it receives from the CN as a basis for defining the resources specified for the RAB, including the maximum data rate for the connection. For clarity, the transmission of the RAB parameters to the AC/PS module 12 is not shown in FIG. 2.

[0037] Along with the number of TrCHs, AC/PS also defines an equal number of Transport Format Sets (TFSs) and Transport Format Combination Set (TFCS) in which the use of multiple TrCHs is taken into account. The TFSs and TFCS so defined are indicated to the MAC sublayer 14 when configuring the MAC sublayer to use demultiplexing (i.e. inverse multiplexing) for downlink and multiplexing for uplink, i.e. when engaging the (transport) channel IMUX/MUX 14 a of the MAC sublayer. Configuring the MAC sublayer is one subtask in the overall task of configuring the RB service in the UTRAN. (See FIG. 5.) The inverse multiplexing according to the invention is thus performed in the RNL, not in the TNL. (See FIG. 4 to compare the RNL to the TNL.)

[0038] Referring still to FIGS. 2A and 2B, in conveying data traffic from the RNC to the Node B 17 a 17 b for a UE 18 (FIG. 2A 2B), the RLC sublayer 13 creates one or more RLC entities 13 a each for providing a radio bearer (RB) for the UE, based on parameters assigned for the RBs by AC/PS. The RLC sublayer 13 then provides the RNC data traffic as a series R1 of RLC PDUs on a logical channel provided by the MAC sublayer 14. The channel IMUX/MUX 14 a takes the R1 series of RLC PDUs and submits them to the FP layer 16 (via PHY, i.e. L1) using a plurality of service access points (SAPs) 16 b corresponding to the plurality of transport channels between the MAC layer and the FP layer, with the distinction according to the invention that the series R1 is divided up into a corresponding plurality of MAC data flows M11 M12 M13 (each MAC data flow being a series of MAC PDUs, i.e. transport blocks, each according to a transport format (TF). The FP layer 16 includes an FP entity 16 a, corresponding to the RB service 13 a, which accepts the MAC PDUs, packages them into FP frames and forwards them to the TNL where AAL2 packets are created. The next step is to communicate these MAC data flows to the Node B 17 a 17 b as TNL data flows (transport bearers) P11 P12 P13 (series of transport blocks in FP frames).

[0039] Still referring to FIGS. 2A and 2B, the dash-dot data flows lines issuing from the AC/PS module 12 represent internal signaling connections between the AC/PS and each of the protocol layers 13 14 15 16, as opposed to the user data indicated by the solid data flows R1, M11, . . . , and P1, . . . In the Node B 17 a 17 b across the Iub interface, there is an FP entity 19 a 19 b that is the peer of the FP entity 16 b in the FP layer 16 of the RNC 11; in the Node B 17 a 17 b, the FP entity 19 a 19 b forwards the received Transport Blocks P11 P12 P13 to L1, which transmits them to the UE 18 through the air interface. Thus, in the RNC 11, the transport blocks P11 P12 P13 are communicated as FP data frames (each containing one or more transport blocks), and delivered to the node B 17 b via the TNL. In FIG. 2B, the peer entity of the MAC-hs entity 20 (in the node B 17 b) resides in the UE 18.

[0040] The operation of the channel IMUX/MUX module 14 a is transparent to the RLC 13 and to the FP entity 16 a, as well as to the TNL generally. The MAC data flows M11 M12 M13 include all the information (in the way of transport format descriptors) needed by the UE 18 to reconstruct the original data traffic from the CN entity that is the source of the data being sent to the UE 18.

[0041] Referring still to FIG. 2, it should be understood that a single FP entity 16 a could be assigned multiple TrCHs, as indicated in FIG. 2 (and indicated by the notation P11 P12 P13), so that only one FP entity 16 a is assigned for the RB provided by the RB service 13 a, or, instead, each TrCh can be assigned a dedicated FP entity which would then provide its own FP traffic flow (as a physical channel). In the latter case, the number of FP data traffic flows must be signaled to the Node B, which would then see each TrCH/FP traffic flow as a separate data traffic flow.

[0042] The invention thus provides that an RNC split (i.e. inverse multiplex) into component (sub) channels a high speed transport channel (e.g. the high speed dedicated shared channel, denominated as HS-DSCH, or the dedicated channel, denominated as DCH) for communication to a UE via a Node B, each component (sub) channel having a bit rate less than a predetermined maximum (e.g. each smaller than 2048 kbit/s). It further provides that the RNC combine (i.e. multiplex) traffic on a plurality of channels be into traffic for a single high speed transport channel for communication to a CN entity.

[0043] It should be understood that although the invention has been shown and described here for downlink only, the invention is also of use for uplink. Implementing the invention for uplink is similar to what is described here for downlink, but the data is received over the air interface by a Node b, and from the Node B the data is transmitted through multiple TrCHs to an RNC.

[0044] It is to be further understood that the above-described arrangements are only illustrative of the application of the principles of the present invention. Numerous further modifications and alternative arrangements besides those indicated above may be devised by those skilled in the art without departing from the scope of the present invention, and the appended claims are intended to cover such modifications and arrangements. 

What is claimed is:
 1. A radio network element (11) for communicating to a mobile user equipment (UE) (18) a higher rate data flow received from a core network (CN) entity, the higher rate data flow being provided to the radio network element (11) at a higher rate than the UE can accept on a single channel, the radio network element(11) characterized by: a) a radio link control (RLC) sublayer (13) including a radio bearer (R1) service (13 a), responsive to the higher rate data flow, for providing a corresponding RLC data flow (R1) for downlink to the UE (18); b) a media access control (MAC) sublayer (14), responsive to the RLC data flow (R1), for providing a plurality of corresponding MAC data flows (M11 M12 M13) at a rate low enough to be acceptable to the UE (18); c) a framing protocol layer (FP layer) (16), responsive to the MAC data flows (M11 M12 M13), for providing corresponding transport network layer data flows (P11 P12 P13); and d) an admission control (AC) (12), responsive to radio access bearer parameters provided by the CN entity, for providing commands to the MAC sublayer (14) specifying how the MAC sublayer (14) is to allocate resources so as to communicate the higher rate data flow to the UE (18); and further characterized by the MAC sublayer (14) in the radio network element including a channel inverse multiplexer/multiplexer (IMUX/MUX) (14 a), responsive to the RLC data flow (R1), for providing the plurality of corresponding MAC data flows (M11 M12 M13) at a rate low enough to be acceptable to the UE (18), and for including with each lower rate data flow (M11 M12 M13) information indicating how the lower rate flows (M11 M12 M13) are to be combined by the UE (18), the lower rate data flows (M11 M12 M13) being suitable for transmission by the FP layer (16) according to a standard protocol not taking into account that the lower rate data flows (M11 M12 M13) are in combination the RLC data flow (R1) corresponding to the higher rate data flow.
 2. The radio network element (11) of claim 1, further characterized in that in sending to a CN entity a plurality of transport network data flows (P11 P12 P13) received from 10 the UE (18), the channel IMUX/MUX (14 a) is further responsive to a plurality of corresponding MAC data flows (M11 M12 M13), and provides, at the direction of the AC (12), a single corresponding RLC data flow (R1) for transmission to the CN entity as a higher rate data flow.
 3. A radio access network including a Node B (16) and also including a radio network element (11) according to claim
 1. 4. A radio access network including a Node B (16) and also including a radio network element (11) according to claim
 2. 5. A method by which a radio network element (11) communicates to a mobile user equipment (UE) (18) a higher rate data flow received from a core network (CN) entity, the higher rate data flow being provided to the radio network element (11) at a higher rate than the UE can accept on a single channel, the method characterized by: a) a step in which a radio link control (RLC) sublayer (13) including a radio bearer (R1) service (13 a), responsive to the higher rate data flow, provides a corresponding RLC data flow (R1) for downlink to the UE (18); b) a step in which a media access control (MAC) sublayer (14), responsive to the RLC data flow (R1), provides a plurality of corresponding MAC data flows (M11 M12 M13) at a rate low enough to be acceptable to the UE (18); c) a step in which a framing protocol layer (FP layer) (16), responsive to the MAC data flows (M11 M12 M13), provides corresponding transport network layer data flows (P11 P12 P13); and d) a step in which an admission control (AC) (12), responsive to radio access bearer parameters provided by the CN entity, provides commands to the MAC sublayer (14) specifying how the MAC sublayer (14) is to allocate resources so as to communicate the higher rate data flow to the UE (18); and further characterized in that the MAC sublayer (14) in the radio network element performs a channel inverse multiplexing/multiplexing using a channel inverse muliplexer/multiplexer (IMUX/MUX) (14 a), responsive to the RLC data flow (R1), and in so doing provides the plurality of corresponding MAC data flows (M11 M12 M13) at a rate low enough to be acceptable to the UE (18), and includes with each lower rate data flow (M11 M12 M13) information indicating how the lower rate flows (M11 M12 M13) are to be combined by the UE (18), the lower rate data flows (M11 M12 M13) being suitable for transmission by the FP layer (16) according to a standard protocol not taking into account that the lower rate data flows (M11 M12 M13) are in combination the RLC data flow (R1) corresponding to the higher rate data flow.
 6. The method of claim 5, further characterized in that in sending to a CN entity a plurality of transport network data flows (P11 P12 P13) received from the UE (18), the channel IMUX/MUX (14 a) is further responsive to a plurality of corresponding MAC data flows (M11 M12 M13), and provides, at the direction of the AC (12), a single corresponding RLC data flow (R1) for transmission to the CN entity as a higher rate data flow. 